Almathera Ten Pack 3: CDPD 3/Almathera Ten on Ten - Disc 3: CDPD3.iso/scope/001-025/scopedisk3/mousecmd/demo.doc

Text File | 1995-03-18 | 6KB | 113 lines

                                MouseCMD DEMO
                                =============

This demo assumes the following:
   That all of the MouseCMD files are in the Current Working Directory (CWD)
       (i.e. when you type DIR<rtn> you get a listing of all of the MouseCMD
       files. In any case, the config file "Config.demo" must be in the CWD
       or the S: directory.
   That Ed (the text editor) is available, along with some other normally
       available commands. None of these are necessary to run MouseCMD; only
       for this demo.

If you're not already RUNning something to read this file (multitasking),
exit that reader program now and do something like:

                           Run Type Demo.doc

This will allow you access to the CLI while you read this file. It would be
much less clumsy to Run a reader program other than Type, of course, that
allows access to multiple files at one time.


                                *  *  *  *


To run the demo (from the Current Working Directory and from the CLI) type:

                           Run MouseCMD Config.demo

Before going further, a hint to make reading the files easier.  MouseCMD has
a drag gadget in its title bar beneath the title "MouseCMD". Use it now to
pull the MouseCMD window down slightly. This will allow easier access to the
depth arrangement gadgets in the "Type" output windows.

You'll probably want to arrange things so that you can, in addition to
reading this file, also read the "Config.demo" file to see how it defines
MouseCMD's commands.  You can do this very easily from MouseCMD (here we go!)
by clicking on the "RUN" button, the "TYPE" button, and the "F" button (left
of "Config.demo").  By depth arranging the windows, you can view both files.
And you now have the first taste of what MouseCMD is all about.

You'll notice some of the buttons leave a space after the text that they
print out, expecting more to follow. Others "press" the Return key to execute
the line. If you examine the Config file you can easily see how its done. Try
building a command yourself by playing with the empty string gadget, then
clicking on the "C" button. If the command didn't "press" the return key,
you can erase it by clicking on "ERASE". You can change the text in any of
the string gadgets whenever you wish. You have to change the Config file to
change the 10 fixed gadgets. Details on writing your own Config file appear
in the Setup.doc file.

A function that greatly enhances the usefulness of MouseCMD is its ability to
redirect its output to another window. You can get a sense of this by
clicking on "N-CLI". This uses the AmigaDOS command "NewCLI" to open a new
CLI window. To redirect MouseCMD's output, click on the "WDW" button, then
anywhere in the new window. In MouseCMD's title bar you will see the new
output confirmed as "WDW:AmigaDOS" changes to "WDW:Send New".

Now, to close the window, click on the "X-CLI" button, then the "<RTN>"
button (I arranged it this way so, hopefully, you wouldn't accidentally send
an EndCLI command to the AmigaDOS window).  The "EndCLI" command is sent to
the new window, it executes, and the window goes away.  You may have noticed
as the new window came and went, by the way, that the FREE MEM display in
MouseCMD's title bar monitored the changing system memory.

Now for something a bit more useful. Assuming "Ed" is available (most of us
probably don't use it, but since everyone has it, it will suffice as an
example), first get rid of some screen clutter by closing the "Type
Config.demo" window. Now "Ed" the same file by pressing the "RUN","Ed", and
"F" buttons.

Perhaps you noticed that the MouseCMD's title bar now indicates that the
window receiving MouseCMD's output has changed back to the AmigaDOS window.
This happens automatically when you try to send output to a window that has
been closed (the last output was going to the NewCLI window, which we
closed).

Ed runs and its window fills the screen, covering the MouseCMD window.  By
now you will probably have rearranged the windows so that MouseCMD appears
over the Ed window. Again, this is very easily done if you have pulled the
MouseCMD window down slightly, below Ed's title bar.

Now redirect MouseCMD's output to the Ed window with the "WDW" button.

MouseCMD uses a fair amount of screen area. It's not much of a problem when
working with AmigaDOS, since everything normally happens at the bottom of the
screen. When reading text, though, you like to see as much as you can. You
can reduce MouseCMD to a "tiny-window" by clicking anywhere on the title bar
between "WDW:" and "MEM". MouseCMD "sleeps" until you reactivate it by
clicking in the tiny-window's window area.

We need some "Ed-style" commands. You'll notice there are 2 buttons labeled
"<--" on the right side of the MouseCMD window. Click on the top one. A new
set of commands appears. Likewise, the bottom button cycles through the
variable command sets. MouseCMD allows you to allocate up to 10 sets of each
type. The demo configuration has allocated 2 sets of each.

You can feel free to fool around with the "Ed" command buttons as long as you
"press" the "QUIT" button last. It's an "Ed" command that exits without
saving changes. Looking at the command text for the "QUIT" button, by the
way, points out the fact that you can string commands together on one button.
Normally you access the Quit command by pressing the Escape key, then Q. Ed
then prompts at the bottom of the screen "Save changes Y/N?" You press the N
key, and the program exits. It all happens in one click from MouseCMD,
however.

That's about it for this quick tour. All of the features are described in
more detail in Setup.doc, as well as instructions on writing your own
commands into a configuration file. To quit MouseCMD, click on its Close
gadget in the upper left corner.

     Bruce Schuldt  630 SW Coral  Junction City, OR 97448  [phone]